\fi-380\li380 Q: I tried to use the Upgrade2.0 app to upgrade to Release 2.0 (or Release 2.1).
\fc0 Everything goes fine until the status says: "
\b copying files from /bin
\b0 ". Then I get an error:
\b Tcl error: Unmatched quote '=>"'
\b0 and the machine just sits there. What can I do?\
\fi0\li0 \
\fi-360\li360 A: This bug in Upgrade2.0 surfaces when
\f1\fs24 /bin/test
\f0\fs28 on the system you are upgrading has been altered or touched. To support the Bourne shell,
\f1\fs24 /bin/[
\f0\fs28 is a link to
\f1\fs24 /bin/test
\f0\fs28 . When Upgrade2.0 sees that
\f1\fs24 /bin/[
\f0\fs28 has been modified, it tries to bring up an attention panel to ask you if the file should be preserved or overwritten. Unfortunately, it becomes confused by the metacharacter in the file's name and an error ensues.\
\
\pard\tx340\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fi-360\li360\fc0 To fix the problem, start up Terminal
\i without
\i0 quitting Upgrade2.0. Su to root and and remove the file (you must quote the filename):\
\f1\fs24 #rm '/UPGRADE2.0/bin/['
\f0\fs28 \
Return to Upgrade2.0. Quit, and restart it. It should be able to pick up the upgrade procedure from the point at which the problem occurred.\
\pard\tx340\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f0\fs28\fi-360\li360\fc0 If you interrupt an upgrade, you can restart Upgrade2.0 and it will automatically resume the upgrade at the point where the problem occurred. When the upgrade resumes, answer any questions the same way you answered them the first time.\